LGTM

Hmm actually do you have any thoughts on how the API would expose the ability to pass configuration values (e.g., other preprocessors that would be run before running nbexecute)? I feel like that could also be useful from the perspective of nbparameterize.

If you don't want to make that part of this PR, no worries, and I'll just merge as is.

how the API would expose the ability to pass configuration values (e.g., other preprocessors that would be run before running nbexecute)?

At least for the case of other preprocessors running before execution, I would suggest running them before calling the function. There's no need to design a new API for running a series of operations in order, because code already defines a series of operations to run in order. ;-)

# Complex
do_y(..., pre_function=do_x)

# Simple
do_x(...)
do_y(...)

We may want to provide similar convenience functions for other preprocessors, so they're easy to call from Python code. But I'd take that on a case-by-case basis.

I notice that this branch has a merge conflict, so I'll resolve those.

Fair enough and fair enough. LGTM, merging.